Release Summary - Jan 12, 2024 (24.01)

PLAT-3677

Platform:

Feed Processing
Developed alert for recommendable products falling below threshold

Developed ‘Alert’ for recommendable products falling below threshold for both feed and streaming clients. If the count of recommendable products is if its below 10% of average of the last 3 days, an alert is raised.

PLAT-3671

Find:

LLM prompt template db changescript

We have implemented a database schema named "llm," which includes the following tables: accounts, prompt_scripts, prompt_templates, prompt_template_properties, prompt_template_versions, and prompt_template_groups.

Users can now see all the necessary tables under llm schema.

ENG-27461

Find:

Implement "delete" action to Fasttrack Assortment

When sending an assortment fast track JSON in the body with a deleted assortment, the products for this assortment are still returned in the response.

The ‘Delete’ functionality has been introduced.

ENG-27269

Find:

Additional special character support in Offmenu

We have successfully added support for additional special characters in Offmenu, enhancing the functionality to accommodate special characters that were not previously covered. This improvement extends support to various special characters, prioritizing those with higher occurrences.

The necessary code changes have been implemented in the search service, including adjustments to the OffMenu query processor and property definitions. These changes ensure that special characters are handled correctly, and the Offmenu functionality now fully supports all specified special characters.

ENG-27181

Find:

Make querytagger item model aware

We have successfully implemented enhancements to make the query tagger item model aware, converting Complementary search JSON to the new format of query understanding. This improvement ensures that the query tagger item model is compatible with the updated format.

PLAT-3690

Find:

Address enrichment attributes in NCA before storing and processing enrichement related data

We have made the necessary enhancements in NCA (to address and check the "catalogSettings" flag before storing enrichment-related data in the catalog database. Previously, even if this flag was set to false, data related to enrichment was still being stored in the catalog database. With this improvement, the flag is properly evaluated and respected, ensuring that enrichment data is handled according to the specified configuration.

For example, when "catalogSettings" specifies that data is not storable in the catalog, this setting is now accurately enforced, preventing unnecessary storage of enrichment data in the catalog database.

PLAT-3676

UPS:

UPS API writer should fail and restart on any error during processing

We have improved the UPS API writer to handle errors more effectively. This enhancement serves two key purposes:

Alerts for Intervention: If there are recurring errors requiring manual intervention, the automatic restart triggers alerts, prompting timely investigation and resolution.

Enhanced Recovery: The service is now better equipped to recover from various failures, such as consumer stalls or initialization errors. This ensures more robust and reliable UPS API request processing.

PLAT-3619

UPS:

Ability to process offline orders without user ID

We have introduced the ability to process offline orders without requiring a user ID. The previous system mandated user IDs for all orders, causing challenges when dealing with a large volume of orders that couldn't be linked to logged-in users.

With this enhancement, we have developed a new version of the Omni Channel API that can accept offline orders without user IDs. During processing, the system utilizes the order ID to consolidate these records into Avro while ensuring they are not persisted unnecessarily in UPS.

ENG-27490

Enterprise Dashboard:

Remove Training Link

Due to the termination of our contract with Litmos, we have removed the training link from the left-hand navigation for all users. This change ensures that the link is no longer accessible or visible to any users of our system.

While we work on finding an alternative training system, we have temporarily hidden the training link to avoid any confusion or inconvenience for our users. We remain committed to providing the best possible experience and resources for our users, and we appreciate your understanding during this transition.

ENG-27084

Engage:

Enhancements to /content API for selecting by tags

In this update, we've significantly improved the Content API, enhancing your ability to filter content with precision using tags. With newly introduced parameters for tag inclusions and exclusions, you now have the flexibility to apply advanced logic, including AND and OR operators when selecting multiple tags. Clear and concise syntax guidelines make implementing these operators easier, ensuring a seamless user experience.

The changes were made to an internal API that is used by the dashboard. This will enable us to improve the filtering options when working with Engage contents.

ENG-27300

Engage:

Enhance tagFilter to allow for Advanced Logic

We have enhanced the tagFilter parameter in the Personalize API. Users can now leverage advanced logic operators such as AND, OR, and NOT to refine their content filtering criteria, providing greater adaptability to match the context of the current page.

With this enhancement, users can create complex filtering expressions by combining tags and logical operators. For instance, you can use expressions like (tag1 OR tag2) AND tag3 or tag1 OR (tag2 AND tag3) to precisely define the content you want to retrieve based on your specific requirements.

ENG-27344

Engineering:

Production testing of streaming recommend discrepancies

Production testing of streaming recommend discrepancies has been done and observations from testing in production and compared them with the ps_catalog version. Please see Jira ticket for detailed report.

PLAT-3661

Recommend:

Multiple content campaigns in a single email to avoid duplication.

The engage content email only served recommends corresponding to a single placement. However, some client wanted to embed multiple content campaigns in a single email and avoid duplication.

ENG-26592

Science:

Added the Image Tagging job to generate color complementary colors to composite outfits

Optimization manager now generates composite outfits with complementary colors.  Composite Outfit uses the color prediction model for complementary colors.

ENG-26979

Science:

Exclude a product in Shop the Look

Merchandisers will now be able to exclude a product from Shop the Look so that it doesn't show as an option to the shopper. The API has been updated to exclude a particular product.

ENG-26978

Science:

Return the configuration for type of overlay Shop the Look

Merchandisers can now select the overlay option (boxes or icons) to be used with all of the Shop the Look products to make the experience easier for the shopper.

Updated the API to return the configuration for which overlay is being used to the portal.

ENG-27454

Find:

Integrate queryUnderstanding section to rr server

We have successfully integrated the queryUnderstanding section into RR Server to enhance query tracking and understanding. The provided parameters, including boost and excludeTerms, are now effectively passed to RR Server for improved query analysis.

ENG-27214

Recommend:

Able to view other clients segment definition

We have resolved an issue where users from one client (Client A or rrportal) were able to access and view the segment definitions of another client (Client B) by manipulating the URL. This behavior posed a significant security risk and was not intended. The issue has been promptly fixed, ensuring the privacy and security of client-specific data, and the functionality now operates as expected.

ENG-27066

Recommend:

UI Error on User Affinity graphs when no user history or no brand history

We've resolved an issue related to User Affinity graphs on the Configuration page. Previously, when there was no user history or no brand history available, an error message was displayed. Now, we've enhanced this behavior to ensure a more graceful handling of such situations.

ENG-27134

Enterprise Dashboard:

Some Compound Strategies show strategies as Deleted in UI

We've resolved a UI display issue related to Compound Strategies, specifically the "Trending_Not_Yet_Viewed" strategy, where two sub-strategies were incorrectly marked as deleted. This problem arose from compound strategy names containing single quotes. Our fix ensures that the UI now accurately reflects the status of sub-strategies within Compound Strategies.

ENG-27259

Enterprise Dashboard:

UI Return to Segment list page if trying to access a segment from another instance

We have resolved an issue in the UI that occurred when users attempted to access a segment created on a different site. Similar to the behavior for Advanced Merchandising rules, the UI now correctly redirects users to the Segment list page when they try to load details for a segment from a different site.

ENG-26786

Enterprise Dashboard:

Find Test Drive not working for large catalogs

We have resolved an issue affecting Find Test Drive for large catalogs. To address this, we have added the necessary &facet.enabled=false parameter to the base request, ensuring the correct functionality of Find Test Drive. Additionally, we have implemented the &fl (filter list) parameter, which filters attribute values displayed in the UI to only include relevant data such as product name, price, and image.

ENG-27212

Enterprise Dashboard:

Shop the Look - Search only recommendable in the portal to find seed products

We have resolved an issue in the Shop the Look feature, ensuring that the portal now exclusively searches for products that are marked as recommendable. Algonomy models are created for recommendable products, and this fix aligns the portal's search functionality with those criteria.

This enhancement ensures that when searching for seed products with bounding boxes, only recommendable products are considered.

ENG-27322

Enterprise Dashboard:

Cannot add one product in an existing restriction rule

We have resolved an issue where users were unable to add multiple products to an existing restriction rule. Previously, when users added a second product and saved the rule, the first product would be removed, leaving only the second product in the rule.

With this fix, users can now add and save multiple products to an existing restriction rule without any products being inadvertently removed.

ENG-27323

Enterprise Dashboard:

Recommend Restrictions - Issue with the Filter products from categories the user has already purchased

We have resolved an issue related to the creation of Conditional Do Not Recommend (DNR) rules when selecting the option "Filter products from categories the user has already purchased." Previously, users encountered an error message when attempting to save such rules.

With this fix, users can now successfully create rules using this option without encountering errors.

ENG-26309

Enterprise Dashboard:

Bug in selecting product in browse boosting rule

We have resolved a bug related to selecting products in a browse boosting rule. Previously, when users started typing a product ID in the input field to add a product (e.g., 73136), they received multiple suggestions in the drop-down. However, the first suggestion displayed the search term itself, and if users clicked on it, it was added as "null(73136)."

With this fix, we have addressed the issue by changing the label from "null" to "unknown." This modification eliminates the misleading behavior, providing a more accurate representation of product selection.

ENG-27340

Enterprise Dashboard:

Social Proof - Message Duration is not retained (Multiple Messages Enabled)

We have addressed an issue in the Social Proof feature related to retaining message duration when multiple messages are enabled. Previously, users encountered a problem where, if they set a message duration (e.g., 5 minutes) and proceeded to the next step, returning to the previous step would reset the duration to 0 minutes.

With this fix, the issue has been resolved, ensuring that the message duration is retained as expected. Users can now set and keep the desired duration when configuring Social Proof messages with multiple messages enabled.

ENG-27253

Data Engineering: Unbale to view statistics data from campaigns

A client was unbale to view statistical data from campaigns, it seems the backend API for the Campaign selector was returning the campaign in the response but was not visible in the UI. The issue has been resolved now.

ENG-27450

Data Engineering:

Unable to swap priorities for created attributes in message type page

User was unable to swap the positions of the created badges in social proof, such as from position 1 to position 2. The issue has been resolved now the user is able to swap created badges.

ENG-27358

Engage:

Product Badging - Change LIST to SINGLE_SELECT_LIST in Badge Template

As backend was not supporting the type: LIST hence it was needed to replace it with "SINGLE_SELECT_LIST" temporarily to unblock. The issue has been resolved now.

ENG-27442

Engage:
The location selector for item page template was not displaying appropriate variables

The location selector for item page template was not displaying appropriate variables for a client, the issue has been resolved now.

ENG-27376

Enterprise Dashboard>Social Message:

Output variable was getting blank automatically

When the user created Social Proof experience, the output variable defined as part of Display Configuration > Display Settings, was getting blank automatically.

After adding a variable when you save and exit the experience and come back immediately to edit It was showing the variable name. However, after some time, it was again going blank. The issue has been resolved now.

ENG-27194

Enterprise Dashboard>Engage:

Incorrect values shown after setting when doing ‘Minimum Should match percentage’ in Search Test Drive under Search Configuration

For a client the parameter ‘Minimum should math percentage’ was not matching available under Search Configuration drop-down. This was happening for Search Test Drive. The value that was set up in the backend JSON config was not shown on Search Configuration drop-down. The issue has been resolved now.

PLAT-3693

Platform> Feed Processing:

Stale(old) enrichment records were not getting deleted

When a new enrichment file got processed, the data was remained in management enrichment tables. However, if the new file has missing entries for some products which were present in an older file, we needed to remove those entries from the table as they were not getting deleted. The issue has been resolved now.

ENG-27334

Science:

Catalog Enrichment job failed with errors

The Catalog Enrichment job failed with errors It failed because of “missing descriptions for site 2090 in HDFS

/science/nlp/content_inputs_automated/1701662414376/descriptions/site_id=2090/*.csv"

The issue has been resolved now.

ENG-27378

Science:

Catalog Enrichment with Wrong Tag Values

Some wrong tags values were generated from the tags.csv file while running ChatGPT Catalog Enrichment for IBT. A code change has fixed the issue.

PLAT-3670

Streaming Catalog:
NCA gets stalled sometimes with common status failing to connect kafka

Occasionally, NCA service is getting stuck and was unable to automatically restart itself when Kafka connectivity issues were encountered. The issue has been resolved now. For this resolution, we have introduced a health check rest API in the native consumer module.

ENG-26207

Find:

Issue with Search Term Reports

We have addressed an issue with the Search Term Reports, where similar sets of search terms were appearing in both the "All Queries - Table" and "0 Results Queries - Table" tabs. This caused incorrect data representation in the reports.

This issue has been fixed now by modifying ViewEvent definitions to be compatible with older ViewEvent.

ENG-26853

3.2.3.1 Medium Severity Findings (Form Manipulation)

We have resolved a form manipulation vulnerability in the application that could potentially lead to unauthorized modifications, user impersonation, and other security issues. Form manipulation occurs when the client modifies fields that are expected to be immutable by the server.

To address this vulnerability, we have implemented a solution that ensures the server does not trust the data returned by the client for read-only fields. Instead, the application maintains the original values of the 'readonly' fields on the server-side, ensuring data integrity.

ENG-26856

3.2.3.4 Medium Severity Findings (Clickjacking)

In response to a clickjacking vulnerability, we have implemented a bug fix to prevent potential attacks in the application. Clickjacking is a security issue where an attacker can trick a user into performing actions on the vulnerable application without their knowledge by overlaying it with an attacker-controlled page.

To address this, we have configured the application to set HTTP response headers that prevent framing by external sources (X-Frame-Options: deny).

ENG-27446

Enterprise Dashboard:

Handle homepage gracefully when Thoughtspot is down

We have resolved an issue where the portal's homepage was not handling ThoughtSpot downtime gracefully. Now, when ThoughtSpot is down, the portal will display an appropriate error message on the homepage, ensuring a better user experience by informing users about the issue and providing them with the necessary information.

ENG-27475

Data Engineering, Enterprise Dashboard:

Data is not displayed for the reports. Showing as Thoughtspot Login page

We have addressed an issue where data was not being displayed for reports, and users were instead encountering the ThoughtSpot login page. Additionally, the homepage was showing an error instead of the expected reports.

The problem has been resolved by updating the CORS (Cross-Origin Resource Sharing) policy in ThoughtSpot to allow the portal.

ENG-27311

Enterprise Dashboard, UPS: Negative Quantities in UPS

We have resolved an issue within the UPS (Unified Personalization Service) where certain orders were displaying negative quantity values. The problem originated from a specific API call that was incorrectly logging a quantity of 1 instead of -1. This discrepancy resulted in orders showing negative quantities in the UPS.

To address this issue, we implemented a solution that ensures each cart view and order now uses a clone of the product details. This approach isolates the product details for each instance, preventing unintended negative quantities from appearing in the UPS. As a result, orders in the UPS will now display the correct quantity values without any negative values.

ENG-26539

Engage:

‘Maximum amount of total views’ functionality didn’t work as expected

Maximum amount of total views functionality was not working as expected the issue has been fixed now.

ENG-27371

RegionFilter is extremely inefficient if region_filter_exception is enabled

The site config region_filter_exception caused the region filter to allow the product's recommendable flag to function instead of a region's inStock in the region filter, in case where a product has no regions.

However, it also checked the condition "product has regional data" which is an expensive way – by loading all of the region data, deserializing it, reading it from disk and so on. The issue has been fixed now.

PLAT-3660

Streaming-Recommend:

Streaming item consumer is not processing Snapshot DELETE and ARCHIVED events sometimes

We addressed an issue where the streaming item consumer was not consistently processing Snapshot DELETE and ARCHIVED events. The problem was related to the ItemStoreSnapshotsQualifier, which sometimes filtered out events for deleted snapshots.